Asylia.io

“Arx, Imperium, Ostium” - Fortress, power, gate.

Asylia.io — Whitepaper
“Arx, Imperium, Ostium”– Fortress, power, gate.

QUICK OVERVIEW (plain English)

What is multi-signature and why do you need it?

Multi-signature (multi-sig) is a proven security mechanism that distributes control over bitcoins among multiple independent keys. A transaction only executes when authorised by at least M of N keys (M-of-N scheme).

  • No single key holds enough power. Neither an attacker nor a negligent user can move funds alone.
  • Key loss ≠ bitcoin loss. You only need M functioning keys.
  • Flexibility of the model. You can include hardware wallets, family, a lawyer or the Asylia vault in the signing process.
  • Customisable permissions. Define how many keys and which combination is required—2-of-3, 3-of-5, 5-of-7…

Multi-sig in one sentence:

Unlocking a bitcoin wallet requires more keys than any single party possesses alone.

  • Private key / seed:
    • The secret code that generates and secures your wallet.
    • Never share it and store it offline (paper, safe, vault).
  • Multi-signature (multi-sig)
    • An M-of-N rule is set. E.g., 2-of-3 signatures → any two of three keys are required to spend.
    • Losing one key doesn’t cost you bitcoins; an attacker with a single key can’t spend them.
  • Asylia as co-signer
    • The platform holds only a backup key and never the majority.
    • Without your signature, funds won’t move, but in a crisis we help finalise the transaction.

Visual representation of multi-sig

For clarity, we’ve prepared a visual of a multi-sig wallet. Imagine our BTC wallet as a chest (with treasure/bitcoins). There are multiple ways to open it, and even through one opening you can access all contents.

Traditional secure wallets as most people know them.
Multi-signature security. Requires 2 keys (of 2) to open.
Multi-signature security. Requires 3 keys (of 3) to open.
Multi-signature security. Requires at least 2 keys (of 3) to open.
Multi-signature security. Requires at least 3 keys (of 5) to open.

In short:

More keys = less risk of loss or theft. Your bitcoins stay in your hands; Asylia is just an insurance policy.

1. Introduction: Why a fortress for Bitcoin?

Phishing, malware, coercion, regulatory pressure and, above all, human error threaten sovereignty over private keys. Multi-signature has historically shown that distributing power among independent parties eliminates a single point of failure and handles unforeseen scenarios (lost key or passphrase, kidnapping, extortion, death, inheritance). Asylia draws inspiration from medieval fortresses—sturdy walls, clear rules and minimal blind trust.

2. Why Asylia.io?

Etymology: Asylia (Greek ἄσυλος) = “sanctuary beyond reach”. Symbolises a place immune to unauthorised intervention. The .io domain alludes to input/output and emphasises reliable, continuous access to your bitcoins.

3. Vision and values

We believe in:

  • Sovereignty and self-sufficiency – keys belong to the user.
  • Security first – design over speed.
  • Interoperability – respecting open Bitcoin standards (BIP-32/39/43/48, PSBT/BIP-174, Descriptors).
  • Open source & auditability – 100 % MIT licence.
  • Integrity – doing the right thing, even when no one’s watching.

We will never allow:

  • Compromises in security or corruption.
  • Speed at the expense of quality.
  • Centralised control or invasion of privacy.

Our promises

  • Independence – free migration to another platform; keys and bitcoins are yours.
  • Security – no compromises; auditable code, verified hardware modules.
  • Transparency – open processes, public roadmap, prompt disclosure of issues.

4. Technical architecture

4.1 Types of multi-sig wallets

  • Backup:
    • 2-of-3: 2 user keys, 1 Asylia key.
    • 2-of-3: 2 user keys, 1 Asylia key.
  • Collaborative signature:
    • 2-of-3 or 3-of-5, keys split among multiple co-signers (family, lawyer, Asylia).
    • Family/business accounts, inheritance, escrow.
  • Advanced multi-sig:
    • Any M-of-N via descriptor.
    • Experienced users with bespoke threat models.

Best practice: 2-of-3 for personal use or 3-of-5 for significant sums. Asylia never holds the quorum—funds cannot move without your participation.

4.2 Keys & hardware

  • Supported HW wallets in MVP: Trezor, Ledger.
  • Asylia’s internal keys: 2-of-3 multi-sig, each key Shamir’s Secret Sharing backed and stored in offline HSM vaults.

4.3 Transaction flow

  • PSBT (BIP-174) generated in web/mobile client.
  • Signature data transfer via platform, QR code, NFC and more.
  • Final transaction broadcast by a public Bitcoin node.

4.4 Recovery modes

  • No-KYC recovery:
    • Offline PDF backup (print and store).
    • Social recovery & time locks (CLTV/CSV) – planned release.
  • Optional KYC recovery – future enterprise edition; no-KYC remains available.

4.5 Technical stack

  • Platform wallet: serverless backend on Supabase (Postgres + Edge Functions / Node.js).
  • Self-custody mode: no central backend; data stored only in encrypted browser localStorage.
  • Fully open source – audits welcome.

5. Who is Asylia.io for?

  • Long-term hodlers and responsible asset stewards.
  • Security-focused professionals and discerning enthusiasts.
  • Families, businesses and trusts requiring collective signing.
  • Anyone seeking uncompromising protection for heirloom assets.

6. Business model & fees

Asylia.io operates with no upfront or ongoing monthly fees. Users may voluntarily include a tip in the transaction as a Bitcoin output.

ItemModel
Basic usage0 % fee – voluntary transaction tip
Recovery via Asylia backup key2.1 % of the spent amount (charged only when platform key used)
Open-source codeMIT licence, community contributions

Proof-of-Concept (PoC) ⚠

Functional but non-production code available at poc.asylia.io and Asylia/poc.
DO NOT USE with real funds.

7. Threat modelling

  • Quorum compromise → multi-sig prevents unilateral loss.
  • Insider threat → open-source, HSM, code reviews, asymmetric signing protocols.
  • Supply-chain attack on HW wallet → hash verification, recommended official firmware.
  • Social engineering & phishing → FIDO2/U2F login, educational content, independent confirmation channels.
  • Infrastructure outage → offline PSBT, IPFS mirror, migration options to other clients.
  • Regulatory pressure → primarily non-custodial SW (MiCA § 4), optional KYC recovery.

8. Community & collaboration

  • Developers & code reviewers – pull requests welcome.
  • BTC & multi-sig experts – BIP standard consultations.
  • Security auditors – bug bounty programme.
  • UX beta testers – iterative client improvements.
  • Sponsors supporting a secure Bitcoin ecosystem.

9. Disclaimer

Asylia.io provides software “as is”. Users bear full responsibility for private key management and legal compliance. Nothing here constitutes legal, tax or investment advice.

Legal context: Asylia is a non-custodial software provider. Under MiCA, not subject to CASP registration.

10. Conclusion: The future is secure

Fortresses of old stood for centuries thanks to strong walls and honourable builders. Asylia adapts this traditional philosophy for the digital age – security, sovereignty and preparedness for generations to come.

“Fiat castrum securitatis, et portae fluctuum non praevalebunt.”
(Let the fortress of security stand, and the gates of storms shall not prevail.)
“Asylia is not here to grow fast. Asylia is here to endure.”

Multi-sig scheme

Backup, co-sig and multi-sig are effectively the same, adhering to the Bitcoin multi-sig standard. The only difference is how they’re used in your wallet.

#
Multi-sig scheme Záloha - 2 of 3
1
Scenario
Single account
Wallet owner - Majority
Key 1
Key 2
Asylia.io
Backup - Minority
Key 3
2
Scenario
Single account
Wallet owner - Majority
Key 1
Key 2
Asylia.io
Backup - Minority
Key 3
3
Scenario
Single account
Wallet owner - Majority
Key 1
Key 2
Asylia.io
Backup - Minority
Key 3
4
Scenario
Single account
Wallet owner - Majority
Key 1
Key 2
Asylia.io
Backup - Minority
Key 3

Our team

“Opus tam validum est quam artifices eius.” – A work is only as strong as its creators.

Dávid Zita

Dávid Zita

Founder & Cto - Core dev.

The founder, author and core developer of Asylia.io is a seasoned technology professional with over a decade of experience in web and mobile app development, security solutions and decentralised technologies. Driven by a personal conviction in sovereignty, privacy and security, they combined their expertise with a deep understanding of Bitcoin principles to create a truly secure and independent custody solution.

Asylia was born of a simple yet firm belief:

“True ownership requires true responsibility.”

Asylia.io is not a marketing experiment but a long-term commitment to building a more secure Bitcoin ecosystem, grounded in honour, traditional values and technical precision.

96df3b9
“Designed and developed in
the Czech Republic”
Built on trust and stability-
© 2025 Asylia.io